Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1133

reference: 858-tree-1
name: 1133
tree-preservation-order: undefined
858-tpo-1
uprn
address-text
point: POINT (-0.954610 50.868093)
geometry: MULTIPOLYGON (((-0.954553 50.868087,-0.954556 50.868098,-0.954564 50.868108,-0.954576 50.868116,-0.954592 50.868121,-0.954609 50.868123,-0.954627 50.868122,-0.954643 50.868117,-0.954656 50.868109,-0.954664 50.868099,-0.954667 50.868088,-0.954664 50.868077,-0.954656 50.868066,-0.954644 50.868058,-0.954628 50.868053,-0.954611 50.868051,-0.954593 50.868053,-0.954577 50.868058,-0.954564 50.868066,-0.954556 50.868076,-0.954553 50.868087)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL